SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Interface (computing)</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Interface (computing)</span></span>

</h1>

</header>

<p>In computing, an <b>interface</b> is a shared boundary across which two or more separate components of a <a href="Computer_system" class="mw-redirect" title="Computer system">computer system</a> exchange information. The exchange can be between <a href="Software" title="Software">software</a>, <a href="Computer_hardware" title="Computer hardware">computer hardware</a>, <a href="Peripheral" title="Peripheral">peripheral devices</a>, <a href="User_interface" title="User interface">humans</a>, and combinations of these.<sup id="cite_ref-HookwayInterface14_1-0" class="reference"><a href="#cite_note-HookwayInterface14-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> Some computer hardware devices, such as a <a href="Touchscreen" title="Touchscreen">touchscreen</a>, can both send and receive data through the interface, while others such as a mouse or microphone may only provide an interface to send data to a given system.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Hardware_interfaces">Hardware interfaces</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Hardware_interface" class="mw-redirect" title="Hardware interface">Hardware interface</a></div>

<p>Hardware interfaces exist in many components, such as the various <a href="Bus_(computing)" title="Bus (computing)">buses</a>, <a href="Computer_data_storage" title="Computer data storage">storage devices</a>, other <a href="I/O" class="mw-redirect" title="I/O">I/O</a> devices, etc. A hardware interface is described by the mechanical, electrical, and logical signals at the interface and the protocol for sequencing them (sometimes called signaling).<sup id="cite_ref-87Blaauw_3-0" class="reference"><a href="#cite_note-87Blaauw-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> A standard interface, such as <a href="SCSI" title="SCSI">SCSI</a>, decouples the design and introduction of computing hardware, such as <a href="I/O" class="mw-redirect" title="I/O">I/O</a> devices, from the design and introduction of other components of a computing system, thereby allowing users and manufacturers great flexibility in the implementation of computing systems.<sup id="cite_ref-87Blaauw_3-1" class="reference"><a href="#cite_note-87Blaauw-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> Hardware interfaces can be <a href="Parallel_communication" title="Parallel communication">parallel</a> with several electrical connections carrying parts of the data simultaneously or <a href="Serial_communication" title="Serial communication">serial</a> where data are sent one <a href="Bit" title="Bit">bit</a> at a time.<sup id="cite_ref-GovindarajaluIBM08_4-0" class="reference"><a href="#cite_note-GovindarajaluIBM08-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Software_interfaces">Software interfaces</h2></div>

<div role="note" class="hatnote navigation-not-searchable">See also: <a href="Application_binary_interface" title="Application binary interface">Application binary interface</a> and <a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">Application programming interface</a></div>

<p>A software interface may refer to a wide range of different types of interfaces at different "levels". For example, an operating system may interface with pieces of hardware. <a href="Application_software" title="Application software">Applications</a> or <a href="Computer_program" title="Computer program">programs</a> running on the operating system may need to interact via data <a href="Stream_(computing)" title="Stream (computing)">streams</a>, filters, and pipelines.<sup id="cite_ref-BuyyaMastering13_5-0" class="reference"><a href="#cite_note-BuyyaMastering13-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> In <a href="Object-oriented_programming" title="Object-oriented programming">object oriented programs</a>, objects within an application may need to interact via <a href="Method_(computer_science)" class="mw-redirect" title="Method (computer science)">methods</a>.<sup id="cite_ref-PooObject08_6-0" class="reference"><a href="#cite_note-PooObject08-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="In_practice">In practice</h3></div>

<p>A key principle of design is to prohibit access to all resources by default, allowing access only through well-defined entry points, i.e., interfaces.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> Software interfaces provide access to computer resources (such as memory, CPU, storage, etc.) of the underlying computer system; direct access (i.e., not through well-designed interfaces) to such resources by software can have major ramifications—sometimes disastrous ones—for functionality and stability.

</p><p>Interfaces between software components can provide <a href="Constant_(computer_science)" class="mw-redirect" title="Constant (computer science)">constants</a>, <a href="Data_type" title="Data type">data types</a>, types of <a href="Subroutine" class="mw-redirect" title="Subroutine">procedures</a>, <a href="Exception_handling" title="Exception handling">exception</a> specifications, and <a href="Method_signature" class="mw-redirect" title="Method signature">method signatures</a>. Sometimes, public <a href="Variable_(programming)" class="mw-redirect" title="Variable (programming)">variables</a> are also defined as part of an interface.<sup id="cite_ref-PattersonComputer04_8-0" class="reference"><a href="#cite_note-PattersonComputer04-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p><p>The interface of a software module <i>A</i> is deliberately defined separately from the <a href="Implementation_(computer_science)" class="mw-redirect" title="Implementation (computer science)">implementation</a> of that module. The latter contains the actual code of the procedures and methods described in the interface, as well as other "private" variables, procedures, etc. Another software module <i>B</i>, for example the <a href="Client_(computing)" title="Client (computing)">client</a> to <i>A</i>, that interacts with <i>A</i> is forced to do so only through the published interface. One practical advantage of this arrangement is that replacing the implementation of <i>A</i> with another implementation of the same interface should not cause <i>B</i> to fail—how <i>A</i> internally meets the requirements of the interface is not relevant to <i>B</i>, which <a href="Separation_of_concerns" title="Separation of concerns">is only concerned</a> with the specifications of the interface. (See also <a href="Liskov_substitution_principle" title="Liskov substitution principle">Liskov substitution principle</a>.)

</p>

<div class="mw-heading mw-heading3"><h3 id="In_object-oriented_languages">In object-oriented languages</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main articles: <a href="Interface_(object-oriented_programming)" title="Interface (object-oriented programming)">Interface (object-oriented programming)</a> and <a href="Concept_(generic_programming)" title="Concept (generic programming)">Concept (generic programming)</a></div>

<p>In some <a href="Object-oriented_programming" title="Object-oriented programming">object-oriented</a> languages, especially those without full <a href="Multiple_inheritance" title="Multiple inheritance">multiple inheritance</a>, the term <i>interface</i> is used to define an <a href="Abstract_data_type" title="Abstract data type">abstract type</a> that acts as an <a href="Abstraction" title="Abstraction">abstraction</a> of a <a href="Class_(computer_science)" class="mw-redirect" title="Class (computer science)">class</a>. It contains no data, but defines behaviours as <a href="Method_(computer_science)" class="mw-redirect" title="Method (computer science)">method</a> signatures. A <a href="Class_(computer_science)" class="mw-redirect" title="Class (computer science)">class</a> having code and data for all the methods corresponding to that interface and declaring so is said to <i>implement</i> that interface.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> Furthermore, even in single-inheritance-languages, one can implement multiple interfaces, and hence can <i>be</i> of different types at the same time.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p><p>An interface is thus a <a href="Data_type" title="Data type">type</a> definition; anywhere an object can be exchanged (for example, in a <a href="Function_(computer_science)" class="mw-redirect" title="Function (computer science)">function</a> or <a href="Method_(computer_science)" class="mw-redirect" title="Method (computer science)">method</a> call) the <i>type</i> of the object to be exchanged can be defined in terms of one of its implemented <i>interface</i>s or base-classes rather than specifying the specific <a href="Class_(computer_science)" class="mw-redirect" title="Class (computer science)">class</a>. This approach means that any class that implements that interface can be used. For example, a <a href="Skeleton_(computer_programming)" title="Skeleton (computer programming)">dummy implementation</a> may be used to allow development to progress before the final implementation is available. In another case, a <a href="Test-driven_development#Fakes,_mocks_and_integration_tests" title="Test-driven development">fake or mock</a> implementation may be substituted during testing. Such <a href="Method_stub" title="Method stub">stub</a> implementations are replaced by real code later in the development process.

</p><p>Usually, a method defined in an interface contains no code and thus cannot itself be called; it must be implemented by non-abstract code to be run when it is invoked. An interface called "<code><a href="Stack_(data_structure)" class="mw-redirect" title="Stack (data structure)">Stack</a></code>" might define two methods: <code>push()</code> and <code>pop()</code>. It can be implemented in different ways, for example, <code>FastStack</code> and <code>GenericStack</code>—the first being fast, working with a data structure of fixed size, and the second using a data structure that can be resized, but at the cost of somewhat lower speed.

</p><p>Though interfaces can contain many methods, they may contain only one or even none at all. For example, the <a href="Java_(programming_language)" title="Java (programming language)">Java</a> language defines the interface <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">Readable</span></code> that has the single <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">read</span><span class="p">()</span></code> method; various implementations are used for different purposes, including <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">BufferedReader</span></code>, <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">FileReader</span></code>, <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">InputStreamReader</span></code>, <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">PipedReader</span></code>, and <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">StringReader</span></code>. <a href="Marker_interface_pattern" title="Marker interface pattern">Marker interfaces</a> like <code class="mw-highlight mw-highlight-lang-java mw-content-ltr" dir="ltr"><span class="n">Serializable</span></code> contain no methods at all and serve to provide run-time information to generic processing using <a href="Reflection_(computer_programming)" class="mw-redirect" title="Reflection (computer programming)">Reflection</a>.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Programming_to_the_interface">Programming to the interface</h3></div>

<p>The use of interfaces allows for a programming style called <i>programming to the interface</i>. The idea behind this approach is to base programming logic on the interfaces of the objects used, rather than on internal implementation details. Programming to the interface reduces dependency on implementation specifics and makes code more reusable.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup>

</p><p>Pushing this idea to the extreme, <a href="Inversion_of_control" title="Inversion of control">inversion of control</a> leaves the <i>context</i> to inject the code with the specific implementations of the interface that will be used to perform the work.

</p>

<div class="mw-heading mw-heading2"><h2 id="User_interfaces">User interfaces</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="User_interface" title="User interface">User interface</a></div>

<p>A <b>user interface</b> is a point of interaction between a computer and humans; it includes any number of <a href="Modality_(human%E2%80%93computer_interaction)" title="Modality (human–computer interaction)">modalities</a> of <a href="Human-computer_interaction" class="mw-redirect" title="Human-computer interaction">interaction</a> (such as graphics, sound, position, movement, etc.) where data is transferred between the user and the computer system.

</p>

<ul><li><a href="Abstraction_inversion" title="Abstraction inversion">Abstraction inversion</a></li>

<li><a href="Application_binary_interface" title="Application binary interface">Application binary interface</a></li>

<li><a href="Application_programming_interface" class="mw-redirect" title="Application programming interface">Application programming interface</a></li>

<li><a href="Business_Interoperability_Interface" class="mw-redirect" title="Business Interoperability Interface">Business Interoperability Interface</a></li>

<li><a href="Computer_bus" class="mw-redirect" title="Computer bus">Computer bus</a></li>

<li><a href="Coupling_(computer_programming)" title="Coupling (computer programming)">Coupling (computer programming)</a></li>

<li><a href="Hard_disk_drive_interface" title="Hard disk drive interface">Hard disk drive interface</a></li>

<li><a href="Implementation_(computer_science)" class="mw-redirect" title="Implementation (computer science)">Implementation (computer science)</a></li>

<li><a href="Implementation_inheritance" class="mw-redirect" title="Implementation inheritance">Implementation inheritance</a></li>

<li><a href="Interoperability" title="Interoperability">Interoperability</a></li>

<li><a href="Inheritance_semantics" class="mw-redirect" title="Inheritance semantics">Inheritance semantics</a></li>

<li><a href="Modular_programming" title="Modular programming">Modular programming</a></li>

<li><a href="Software_componentry" class="mw-redirect" title="Software componentry">Software componentry</a></li>

<li><a href="Virtual_inheritance" title="Virtual inheritance">Virtual inheritance</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFHookway,_B.2014" class="citation book cs1">Hookway, B. (2014). "Chapter 1: The Subject of the Interface". <a rel="nofollow" class="external text" href="https://books.google.com/books?id=BQM_AwAAQBAJ"><i>Interface</i></a>. MIT Press. pp. <span class="nowrap">1–</span>58. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780262525503</bdi>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite class="citation encyclopaedia cs1"><i>IEEE 100 - The Authoritative Dictionary Of IEEE Standards Terms</i>. NYC, NY, USA: IEEE Press. 2000. pp. <span class="nowrap">574–</span>575. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780738126012</bdi>.</cite></span>

</li>

<cite id="CITEREFBlaauwBrooks,_Jr.1997" class="citation cs2">Blaauw, Gerritt A.; Brooks, Jr., Frederick P. (1997), "Chapter 8.6, Device Interfaces", <i>Computer Architecture-Concepts and Evolution</i>, Addison-Wesley, pp. <span class="nowrap">489–</span>493, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-201-10557-8</bdi></cite>

See also:

<cite id="CITEREFPattersonHennessey2005" class="citation cs2">Patterson, David A.; Hennessey, John L. (2005), "Chapter 8.5, Interfacing I/O Devices to the Processor, Memory and Operating System", <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/isbn_9781558606043/page/588"><i>Computer Organization and Design - The Hardware/Software Interface, Third Edition</i></a></span>, Morgan Kaufmann, pp. <a rel="nofollow" class="external text" href="https://archive.org/details/isbn_9781558606043/page/588">588–596</a>, <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55860-604-1</bdi></cite></span>

</li>

<li id="cite_note-GovindarajaluIBM08-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-GovindarajaluIBM08_4-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFGovindarajalu,_B.2008" class="citation book cs1">Govindarajalu, B. (2008). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=Hyl8SA1eHzIC&pg=PA142">"3.15 Peripheral Interfaces and Controllers - OG"</a>. <i>IBM PC And Clones: Hardware, Troubleshooting And Maintenance</i>. Tata McGraw-Hill Publishing Co. Ltd. pp. <span class="nowrap">142–</span>144. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780070483118</bdi><span class="reference-accessdate">. Retrieved <span class="nowrap">15 June</span> 2018</span>.</cite></span>

</li>

<li id="cite_note-BuyyaMastering13-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-BuyyaMastering13_5-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFBuyya,_R.2013" class="citation book cs1">Buyya, R. (2013). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=VSDZAgAAQBAJ&pg=SA2-PA13"><i>Mastering Cloud Computing</i></a>. Tata McGraw-Hill Education. p. 2.13. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781259029950</bdi>.</cite></span>

</li>

<li id="cite_note-PooObject08-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-PooObject08_6-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFPoo,_D.Kiong,_D.Ashok,_S.2008" class="citation book cs1">Poo, D.; Kiong, D.; Ashok, S. (2008). "Chapter 2: Object, Class, Message and Method". <a rel="nofollow" class="external text" href="https://archive.org/details/springer_10.1007-978-1-84628-963-7"><i>Object-Oriented Programming and Java</i></a>. Springer-Verlag. pp. <span class="nowrap">7–</span>15. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781846289637</bdi>.</cite></span>

</li>

<cite id="CITEREFBill_Venners2005" class="citation web cs1">Bill Venners (2005-06-06). <a rel="nofollow" class="external text" href="http://www.artima.com/lejava/articles/designprinciples.html">"Leading-Edge Java: Design Principles from Design Patterns: Program to an interface, not an implementation - A Conversation with Erich Gamma, Part III"</a>. <i>artima developer</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110805191904/http://www.artima.com/lejava/articles/designprinciples.html">Archived</a> from the original on 2011-08-05<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-08-03</span></span>. <q>Once you depend on interfaces only, you're decoupled from the implementation. That means the implementation can vary, and that is a healthy dependency relationship. For example, for testing purposes you can replace a heavy database implementation with a lighter-weight mock implementation. Fortunately, with today's refactoring support you no longer have to come up with an interface up front. You can distill an interface from a concrete class once you have the full insights into a problem. The intended interface is just one 'extract interface' refactoring away. ...</q></cite></span>

</li>

<li id="cite_note-PattersonComputer04-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-PattersonComputer04_8-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFPatterson,_D.A.Hennessy,_J.L.2004" class="citation book cs1">Patterson, D.A.; Hennessy, J.L. (7 August 2004). <i>Computer Organization and Design: The Hardware/Software Interface</i> (3rd ed.). Elsevier. p. 656. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780080502571</bdi>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://docs.oracle.com/javase/tutorial/java/concepts/interface.html">"What Is an Interface"</a>. <i>The Java Tutorials</i>. Oracle. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120412093619/http://docs.oracle.com/javase/tutorial/java/concepts/interface.html">Archived</a> from the original on 2012-04-12<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-05-01</span></span>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://docs.oracle.com/javase/tutorial/java/IandI/createinterface.html">"Interfaces"</a>. <i>The Java Tutorials</i>. Oracle. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120526080117/http://docs.oracle.com/javase/tutorial/java/IandI/createinterface.html">Archived</a> from the original on 2012-05-26<span class="reference-accessdate">. Retrieved <span class="nowrap">2012-05-01</span></span>.</cite></span>

</li>

<cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.precisejava.com/javaperf/j2se/Serialization.htm">"Performance improvement techniques in Serialization"</a>. Precise Java. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110824150046/http://www.precisejava.com/javaperf/j2se/Serialization.htm">Archived</a> from the original on 2011-08-24<span class="reference-accessdate">. Retrieved <span class="nowrap">2011-08-04</span></span>. <q>We will talk initially about Serializable interface. This is a marker interface and does not have any methods.</q></cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite id="CITEREFGammaHelmJohnsonVlissides1995" class="citation book cs1">Gamma; Helm; Johnson; Vlissides (1995). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/designpatternsel00gamm"><i>Design Patterns: Elements of Reusable Object-Oriented Software</i></a></span>. Addison Wesley. pp. <a rel="nofollow" class="external text" href="https://archive.org/details/designpatternsel00gamm/page/17">17–18</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780201633610</bdi>.</cite></span>

</li>

</ol></div></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1038841319">

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-label="Navbox772" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Authority control databases: National </th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4053059-0">Germany</a></span></li><li><span class="uid"><span class="rt-commentedText tooltip tooltip-dotted" title="počítačová rozhraní"><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph115863&CON_LNG=ENG">Czech Republic</a></span></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007545775905171">Israel</a></span></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-29" href="https://en.wikipedia.org/wiki/?title=Interface_(computing)&oldid=1303147805">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>